Frequently Asked Questions (FAQs)

The 360 survey evaluation relationship entry API supports the following evaluation relationship types: superior, subordinate, colleague, other, and self-evaluation. These are the standard 360-degree assessment relationship types, covering the various hierarchy levels and role relationships within an organization.

The configuration rules for evaluation relationship level names are as follows: 1. The page supports 10 levels, while the API supports 99 levels; 2. It supports adding and modifying level names; 3. The name length of each level is limited to 60 characters. This means the system displays 10 levels in the user interface, but the backend API can handle up to 99 levels.

The validation rules for email addresses and mobile phone numbers in evaluation relationship entry are as follows: 1. Email addresses and mobile phone numbers can be entered; 2. They must correspond one-to-one, and duplicates are not allowed; 3. The system will verify the uniqueness of the email addresses and mobile phone numbers to ensure that each evaluator has a unique contact method.

The length limit rules for evaluation relationship entry are as follows: 1. The name length limit for the name is 64 characters; 2. The name length limit for the level is 60 characters. These limits ensure data consistency and system stability.

The many-to-many relationship rules for evaluation relationships are as follows: 1. The same person being evaluated can have multiple evaluators; 2. The same evaluator can evaluate multiple people; 3. This design supports complex organizational assessment structures, allowing one person to be evaluated by multiple people while also enabling one person to evaluate multiple people.

The validation rules for self-evaluator entry are as follows: 1. The name entered for the self-evaluator must be the same as the name of the person being evaluated; 2. If they do not match, the entry will fail; 3. This rule ensures the accuracy of the self-evaluation relationship and prevents incorrect self-evaluation relationship entries.

The add and append modes of the add evaluation relationship API are distinguished by the is_delete_for_prev_eval_rel field: 1. If it is true, it is the add mode, which will delete the previous evaluation relationship; 2. If it is false, it is the append mode, which will add new evaluation relationships based on the existing ones.

The restriction rules for re-importing evaluation relationships when response sheets already exist are as follows: 1. The frontend page does not support re-importing evaluation relationships; 2. In the API, when is_delete_for_prev_eval_rel is true, re-importing is restricted; 3. This restriction prevents accidental operations that could lead to data loss when response data already exists.

The following questionnaire types do not support evaluation relationship entry and adding evaluation levels: 1. Non-existent questionnaires; 2. Non-360-degree questionnaires. Only valid 360-degree questionnaires support the evaluation relationship entry and evaluation level addition functions, ensuring the applicability of the feature and the accuracy of the data.

The business acceptance criteria for the 360 survey evaluation relationship entry API include: 1. Correctly supports five types of evaluation relationships (superior, subordinate, colleague, other, self-evaluation); 2. Level name configuration complies with length and quantity limits; 3. Email and mobile number uniqueness validation works correctly; 4. Name and level name length limits are effective; 5. Many-to-many relationship handling works correctly; 6. Self-evaluator name consistency validation is effective; 7. The distinction between add and append modes is correct; 8. Restriction rules take effect when answers already exist; 9. Restriction rules take effect for non-360-degree surveys.